Method and system for reporting events in telecommunication networks

ABSTRACT

Methods and systems are provided for reporting to subscribers, wireless network events in a plurality of formats and languages depending upon the particular subscriber group to which a wireless subscriber belongs. When a subscriber requests a call, a switching node in the network invokes a trigger that identifies a location register for routing the call and sends a route request to the location register. While processing the route request, if the location register detects an event that would prevent the call from being routed, the location register identifies the subscriber group of the wireless subscriber and determines a directory number associated with the identified subscriber group and the detected event. The location register then returns the determined directory number to the switching node. Using the determined directory number, the switching node establishes the call to a message node, where a message associated with the determined directory number is executed. Accordingly, the wireless network reports the detected event in a format and language that the wireless subscriber, or an entity attempting to communicate with the wireless subscriber, can recognize.

RELATED APPLICATIONS

The present application is a continuation-in-part of application Ser.No. 09/418,436, filed Oct. 14, 1999.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to telecommunication networks and, moreparticularly, to a method and system for reporting events to subscribersin telecommunication networks.

2. Background of the Art

Telecommunication networks use various signaling systems forestablishing calls between subscribers. At times, however, the networksmay detect certain states or events that would prevent the networks fromestablishing calls between subscribers. These events may include, forexample, when a called directory number is out of service, network linesare busy or down, a switching node experiences a problem, etc. In suchinstances, the networks instead report the detected events to thesubscribers by playing prerecorded audible messages.

Specifically, when a subscriber places a call to another subscriber in anetwork, a switching node local to the calling subscriber receives acall request from the calling subscriber's device. The switching nodethen sends a route request to a signaling node in the network todetermine a route for the call. If the signaling node determines aroute, the signaling node returns to the switching node the directorynumber of the next node in the network through which the call must berouted. Otherwise, if the signaling node detects that the call cannot beestablished or routed such as when the called subscriber's directorynumber is out of service, the signaling node returns an error code tothe switching node. The switching node then notifies the subscriber thatthe requested call cannot be established by playing a prerecordedaudible message corresponding to the error code.

Although audible messages may be sufficient for reporting events tosubscribers who use plain ordinary telephone service (POTS) telephonesets, such messages are not universally recognizable by all subscriberdevices. For example, consider a subscriber who uses atelecommunications device for the deaf (TDD) to place calls to othersubscribers in the network. When the network plays an audible message toreport an event, neither the subscriber nor the TDD device would be ableto recognize the message. Similarly, an application running in a desktopcomputer for dialing into, for example, a local Internet ServiceProvider (ISP) system cannot recognize audible messages received fromthe network or present such messages in a form that is recognizable to asubscriber.

In present wireline telecommunications networks, a wireline telephonenumber or directory number (DN) is associated with a fixed geographiclocation and is served by a single wireline switch. A wireless DN,however, is associated with multiple geographic locations and is servedby any one of a number of wireless switches depending on the specificgeographic location of the associated wireless device at the time a callis made. This portability of a wireless DN is one of the basicattributes of wireless telephony.

A home location register and visited location register in atelecommunications network provide seamless roaming when a call isplaced to or from a wireless DN. A home location register is associatedwith a home wireless switch where a wireless DN resides (i.e., thewireless switch to which all incoming calls to the wireless DN aredirected). A wireless device is located within its home area when thewireless device can directly communicate with its associated homewireless switch (i.e., located in the area covered by the home wirelessswitch).

A visitor location register is associated with a wireless switchcurrently serving a wireless device that is outside of its home area. Awireless device is outside of its home area (or roams) when the wirelessdevice cannot directly communicate with the home wireless switch andinstead communicates with another wireless switch, which is referred toas a visited wireless switch.

In telecommunication networks two connections must be established when acall is placed to a wireless DN whose associated wireless device isoutside of its home area. In such instances, the telecommunicationsnetwork first establishes a connection to the home wireless switchassociated with the wireless DN. The home wireless switch thenestablishes a second connection to a visited wireless switch thatcurrently serves the wireless DN. When errors, such as missinginformation, misrouted query and other process failures are encountered,a numerical error value is returned to the requester representing thereason for the failure.

There are multiple messages used in wireless intelligent networks (WIN)that route call requests from wireless subscribers or from users who useaudible devices such as, plain ordinary telephone service (POTS)telephone sets, attempting to communicate with the wireless subscribers.These include, but are not limited to, the LocationRequest,RoutingRequest, OriginationRequest and TerminationRequest messagesdescribed in “Interim Standard 41” (IS-41). The IS-41 standard isdescribed in “Radio Telecommunications Intersystem Operations,”ANSI/TIA/EIA/41-D-1997, which is incorporated herein by reference.Although used in different circumstances, each of these messagesultimately requests a Directory Number which to route the call requests.

As an illustration, FIG. 10 shows a block diagram of a conventionalTelecommunication network (1000) implementing the LocationRequest,RoutingRequest messages. Telecommunications network 1000 comprises awireline switch 1020, a home wireless switch 1040, a home locationregister (HLR) 1050, signal transfer points (STPs) 1060, 1087 and 1057,a visitor location register (VLR)1070, a visited wireless switch 1080, awireline telephone 1010, antenna 1090, and a wireless device 1095.

Typically, a wireline subscriber using telephone 1010 initiates a callrequest by dialing the wireless DN associated with wireless device 1095,temporarily located in a visited system controlled by visited wirelessswitch 1080. The request is sent to wireline switch 1020 over existingconnection 1000 a, where it examines the DN to determine its status(resident or non-resident). When wireline switch recognizes thenon-resident status of the number, it routes the request 1000 b toPublic switch Telephone Network/Interchange Carrier (PSTN/IXC) 1030 overexisting connection 1000 b. PSTN/IXC 1030 examines the dialed number androutes it to home wireless switch 1040, using existing connection 1000c.

Home wireless switch 1040 recognizes the DN as one that it is notcurrently serving, and sends an IS-41 LocationRequest message 1000 d toHLR 1050, possibly through STP 1057. HLR 1050 examines its database anddetermines that the wireless device 1095 is being served by VLR 1070,which is associated with the visited wireless switch 1080. HLR 1050sends an IS-41 RoutingRequest 1000 e to VLR 1070, possibly by way of STP1060.

VLR 1070 consults its internal database and allocates a Temporary LocalDirectory Number (TLDN) from a pool of available numbers associated withvisited wireless switch 1080 currently serving wireless device 1095. TheTLDN is populated into the response to the RoutingRequest 1000 e andsent back to HLR 1050 as RoutingRequest response 1000 f, possibly by wayof STP 1060.

HLR 1050 takes the TLDN from the RoutingRequest response 1000 f andpopulates it into the response to the LocationRequest 1000 d from homewireless switch 1040, as LocationRequest response 1000 g. Home wirelessswitch 1040 examines the LocationRequest response 1000 g and establishesthe route to the TLDN by way of PSTN/IX 1035. The PSTN/IX 1035establishes a route to the visited wireless switch 1070 and passes thecall via connection 1000 i. The visited wireless switch 1080 sends aRoutingRequest 1000 j to VLR 1070 possibly through STP 1087, andreceives a response 1000 k containing a mobile identification number(MIN) previously associated with the TLDN populated into RoutingRequestresponse 1000 f. The visited wireless switch 1070 then routes the callto the wireless device 1095 by way of antenna 1090 using internalrouting 10001. Thus, wireline telephone 1010 is connected to wirelessdevice 1095 by a voice path consisting of a subscriber line 1000 a,wireline switch 1020, connection 1000 b, PSTN/IX 1030, connection 1000c, home wireless switch 1040, connection 1000 h, PSTN/IX 1035,connection 1000 i, visited wireless switch 1080, internal connection10001, and antenna 1090.

It should be noted that STPs 1057, 1060 and 1087 may represent one ormore STPs that are required to perform the transfer of messages.Furthermore, the communications between VLR 1070 and HLR 1050, visitedwireless switch 1080 and VLR 1070, and between home wireless switch 1040and HLR 1050, may take place without STPs 1060, 1087 and 1057,respectively.

Event reporting (including error handling) occurs whereby an error codeis returned in the response to either the RoutingRequest orLocationRequest (depending on the entity encountering the exceptioncondition). This error would propagate back to the original requestingparty, the home wireless switch 1040, which would map the event/error toone of the standard recordings already available on the switch. Examplesof events that might be reported are Subscriber Not available [No PageResponse], No Capacity [Resource Shortage] and Busy.

FIG. 11 shows a block diagram of a conventional Telecommunicationnetwork (1100) implementing the OriginationRequest message.Telecommunications network 1100 comprises a wireline switch 1180, a homelocation register 1160, signal transfer points (STPs) 1150 and 1147, avisitor location register 1140, a visited wireless switch 1130, awireline telephone 1190, antenna 1120, and a wireless device 1110.

Typically, wireless device 1110 originates a call at visited wirelessswitch 1130 by way of antenna 1120 and existing internal connectivity1100 a. Visited wireless switch 1130 recognizes parameters previouslyprovided by home location register (HLR) 1160, causing an originationtrigger to be invoked, which locates a visited location register (VLR)associated with the visited wireless switch 1130. This results in anOriginationRequest 1100 b to be sent to VLR 1140, possibly through STP1147.

VLR 1140 passes the OriginationRequest 100 b to HLR 1160, possibly byway of STP 1150. HLR consults its internal tables and routinginformation to determine if the dialed call is allowed, possiblysubstituting a different destination number into a OriginationRequestresponse 1100 c. The OriginationRequest response 1100 c is passed backto the visited wireless switch 1130 by way of VLR 1140 and possibly STPs1150 and 1147.

It should be noted that STPs 1150 and 1147 may represent one or moreSTPs that are required to perform the transfer of messages. Furthermore,the communications between VLR 1140 and HLR 1160, and visited wirelessswitch 1130 and VLR 1140, may take place without STPs 1150 and 1147,respectively.

The visited wireless switch 1130 routes the call to the destinationnumber returned in the OriginationRequest response 1100 c by way ofexisting connection 1100 d to PSTN/IX 1170. The call is routed byPSTN/IX 1170 to wireline switch 1180, where the destination numberresides, by way of existing connection 1100 e. Wireline switch 1180routes the call to wireline telephone 1190.

The overall differentiation here from an ordinary wireless call is thateach call made by the wireless device 1110 is validated by HLR 1160, andthe actual destination connected to is that specified by HLR 1160through the destination number contained in the OriginationRequestresponse 1100 c, which may be the same or different from the numberdialed by the wireless device 1110.

Analogous to the description of FIG. 10, event reporting (includingerror handling) occurs whereby an error code is returned in the responseto the OriginationRequest. This error would propagate back to theoriginal requesting party, the visited wireless switch 1130, which wouldmap the event/error to one of the standard recordings already availableon the switch. Examples of events that might be reported are No Capacity[Resource Shortage] and Unassigned Directory Number.

FIG. 12 shows a block diagram of a conventional Telecommunicationnetwork 1200 implementing the TerminationRequest message.Telecommunications network 1200 comprises a wireline switch 1220, PSTNnetwork 1230, a home wireless switch 1240, a home location register1250, STP 1257, a wireline telephone 1210, antenna 1260, and a wirelessdevice 1270.

Typically, a wireline telephone 1210 attempts to place a call towireless device 1270 by utilizing existing connection 1200 a to wirelineswitch 1220. Wireline switch 1220 routes the call through existingconnection 1200 b to PSTN/IX 1230. PSTN/IX 1230, using existingconnection 1200 c, passes the call to home wireless switch 1240. Homewireless switch 1240 recognizes parameters previously provided by HLR1250, causing a termination trigger to be invoked, which locates a HLRassociated with the visited wireless switch 1230, in this case HLR 1250.Home wireless switch 1240 subsequently provides a TerminationRequest1200 d to HLR 1250, possibly through STP 1257.

HLR 1250 consults internal tables and routing information to determineif the dialed call is allowed, and possibly substitutes a differentphone number into a TerminationRequest response 1200 e. TheTerminationRequest response 1200 e is passed back to the home wirelessswitch 1240, possibly through STP 1257. The home wireless switch 1240may then route the call to the wireless device 1270 by way of internalconnection 1200 f and antenna 1260. The advance described here is theability of HLR 1250 to examine the call attempt to the wireless device1270 and specify the actual termination directory number.

It should be noted that STP 1257 may represent one or more STPs that arerequired to perform the transfer of messages. Furthermore, thecommunications between home wireless switch 1240 and HLR 1250, may takeplace without STP 1257.

Similar to the description of FIGS. 10 and 11, event reporting(including error handling) occurs whereby an error code is returned inthe response to the TerminationRequest. This error would propagate backto the original requesting party, the home wireless switch 1240, whichwould map the event/error to one of the standard recordings alreadyavailable on the switch. Examples of events that might be reported areNo Capacity [Resource Shortage] and Unassigned Directory Number.

With reference to the networks described in FIGS. 10–12, problems arisein returning the reason for the failure to the party that originated thecall, enabling them to correct their actions, if possible, and retrytheir call. Current technology provides only for the requester tointerpret the error value according to a standard definition and providetheir own routing to an audible error message. Because of using only afixed audible recording technology for the error report, automated anddata-only calls may fail to provide usable information to the calloriginator. For example, an audible message has little value to ahearing impaired user attempting a call using a TelecommunicationsDevice for the Deaf (TDD). Similarly, an application running in adesktop computer for dialing into, for example, a local Internet ServiceProvider (ISP) system cannot recognize audible messages received fromthe network or present such messages in a form that is recognizable tothe wireless subscriber. With calls in a wireless intelligent networkoriginating from multiple sources and performing requests for routinginformation from multiple sources, the problem of providing thisinformation in a meaningful format for specific users growsgeometrically with the size of the Intelligent Network (IN).Additionally, error sources that are not specific to the IN but may bemeaningful to the applications cannot be reported without expanding thestandard offering for the IN.

As yet another example, consider subscriber devices used in automotivetelemetric or remote reading applications. In such applications,subscriber devices send and receive data from remote systems byautomatically placing calls over existing networks. However, since thesesubscriber devices cannot process the audible messages that are reportedby the networks, they cannot provide the subscriber with informative asto the cause of most communication failures. Furthermore, thesesubscriber devices cannot automatically take corrective actions inresponse to most communication failures. Corrective actions may include,for example, redialing a directory number when network lines are busy ordialing a different directory number when a previously dialed directorynumber is temporarily out of service. As the number of subscribers whouse these and other devices that cannot process audible messagesincreases, the need for reporting network events in formats thatsubscriber devices can process grows accordingly.

Furthermore, even with respect to those users who use audible devicessuch as, plain ordinary telephone service (POTS) telephone sets, tocommunicate with wireless subscribers there is a need to provide audiblemessages in languages that both the users and subscribers canunderstand. For example, a Spanish speaking subscriber may wish toreceive audible messages in Spanish, whereas a French speakingsubscriber may wish to receive audible messages in French. The utilityof this process recognizes that if a wireless subscriber utilizes aspecial data type (such as TDD), or language (such as French), forcommunication, then those who wish to communicate with the wirelesssubscriber will also be expecting the same format.

SUMMARY OF THE INVENTION

It is therefore desirable to have a method and system for reportingevents in formats and languages that are recognizable by subscribers intelecommunication networks.

Methods and systems consistent with the present invention report networkevents to subscribers in a plurality of formats and languages dependingupon the particular subscriber group to which a subscriber belongs. Whenan event is detected, such methods and systems identify a subscriber'sgroup, determine a directory number associated with the identified groupand the detected event, and report to the subscriber a messageassociated with the determined directory number.

In accordance with an embodiment of the invention, a switching node isconfigured with a trigger that designates a signaling node in thenetwork for routing call requests received by the switching node fromsubscribers in the network. The designated signaling node is configuredwith a directory number mapping table that includes a plurality ofpredetermined directory numbers indexed according to events, which whendetected are reported to the calling subscribers such as, when asubscriber's directory number is out of service, network lines are busyor out of service, etc. These predetermined director numbers are furtherindexed according to subscriber groups in the network.

The predetermined directory numbers are selected so that they terminateat a message node such as, a messaging system, in the network, where aplurality of stored messages are associated with the predetermineddirectory numbers, respectively. These messages may be stored in aplurality of formats and languages such as, voice, data,telecommunications for the deaf (TDD), English, Spanish, etc. dependingupon the particular subscriber groups in the network.

When a switching node receives a request for a call from a callingsubscriber to a called subscriber, the switching node invokes thetrigger configured therein to identify the signaling node designated forrouting calls from the calling subscriber and sends a route request tothe identified signaling node. While processing the route request, ifthe signaling node detects an event that should be reported to thecalling subscriber, the signaling node identifies the subscriber groupassociated with the calling subscriber. The signaling node then selectsa directory number from the directory number mapping table based on thedetected event and the identified subscriber group and returns theselected directory number to the switching node. Based on the directorynumber received from the signaling node, the switching node establishesa call between the calling subscriber and the message node, where amessage associated with the directory number is executed.

Accordingly, the network reports the detected event in a format andlanguage that the calling subscriber or its device can recognize. As anillustration, when a calling subscriber dials a directory number and thenetwork detects an event such as, an error that must be reported to thecalling subscriber, that event is reported in a TDD format to a callingsubscriber using a TDD device, whereas the same event is reported in avoice format to a calling subscriber using a POTS telephone set.Furthermore, events are reported in English to a calling subscriberwhose subscriber group profile indicates that events should be reportedin English, whereas the same events are reported in Spanish to a callingsubscriber whose subscriber group profile indicates that events shouldbe reported in Spanish.

In an alternate embodiment of the present invention, the event reportingtechniques are implemented in a wireless telecommunications environment.In accordance with this embodiment of the invention, a switching nodepasses call requests to a designated location register in the networkfor routing the call requests received by the switching node fromentities attempting to communicate with wireless subscribers in thenetwork. The designated location register is configured with a directorynumber mapping table that includes a plurality of predetermineddirectory numbers indexed according to events, which when detected, arereported to the entities attempting to communicate with the wirelesssubscribers. These events include, but are not limited to, SubscriberNot Available [No Page Response], No Capacity [Resource Shortage] andBusy. These predetermined directory numbers are further indexedaccording to subscriber groups in the network.

The predetermined directory numbers are selected so that they terminateat a message node such as, a messaging system, in the network, where aplurality of stored messages are associated with the predetermineddirectory numbers, respectively. These messages may be stored in aplurality of formats and languages such as, voice, data,telecommunications for the deaf (TDD), English, Spanish, etc. dependingupon the particular subscriber groups in the network.

When a switching node receives a request for a call from a callingwireless subscriber to a called user or device, the switching nodeinvokes the trigger configured therein to identify a location registerdesignated for routing calls from the calling wireless subscriber andsends a request to the identified location register. While processingthe request, if the location register detects an event that should bereported to the calling wireless subscriber, the location registeridentifies the subscriber group associated with the calling subscriber.The location register then selects a directory number from the directorynumber mapping table based on the detected event and the identifiedsubscriber group and returns the selected directory number to theswitching node. Based on the directory number received from the locationregister, the switching node establishes a call between the callingwireless subscriber and a message node, where a message associated withthe directory number is executed.

Accordingly, the network reports the detected event in a format andlanguage that the calling wireless subscriber or its device canrecognize. As an illustration, when a calling wireless subscriber dialsa directory number and the network detects an event such as, an errorthat must be reported to the calling subscriber, that event is reportedin a TDD format to a calling subscriber using a TDD device, whereas thesame event is reported in a voice format to a calling subscriber using aPOTS telephone set. Furthermore, events are reported in English to acalling subscriber whose subscriber group profile indicates that eventsshould be reported in English, whereas the same events are reported inSpanish to a calling subscriber whose subscriber group profile indicatesthat events should be reported in Spanish.

Additionally, the network reports the detected event in a format andlanguage that a calling user, or device, attempting to communicate witha wireless subscriber using a TDD device, can recognize. As anillustration, when a calling entity dials a directory number and thenetwork detects an event such as, an error that must be reported to thecalling entity, that event is reported in a TDD format, whereas the sameevent is reported in a voice format to a calling entity attempting tocommunicate with a wireless subscriber using a POTS telephone set.Furthermore, events are reported in English to a calling entityattempting to communicate with a subscriber whose subscriber groupprofile indicates that events should be reported in English, whereas thesame events are reported in Spanish to a calling entity attempting tocommunicate with a wireless subscriber whose subscriber group profileindicates that events should be reported in Spanish.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary and the following detailed description should notrestrict the scope of the claimed invention. Both provide examples andexplanations to enable others to practice the invention. Theaccompanying drawings, which form part of the description of theinvention, show several embodiments of the invention, and together withthe description, explain the principles of the invention.

In the Figures:

FIG. 1 is a block diagram of a telecommunications network, in accordancewith methods and systems consistent with the invention;

FIG. 2 is a block diagram of a switching node in a telecommunicationsnetwork, in accordance with methods and systems consistent with theinvention;

FIG. 3 is a block diagram of a trigger table in a switching node, inaccordance with methods and systems consistent with the invention;

FIG. 4 is a block diagram of a signaling node in a telecommunicationsnetwork, in accordance with methods and systems consistent with theinvention;

FIG. 5 is a block diagram of a directory number mapping table in asignaling node, in accordance with methods and systems consistent withthe invention;

FIG. 6 is a block diagram of a message node in a telecommunicationsnetwork, in accordance with methods and systems consistent with theinvention;

FIG. 7 is a block diagram of a network interface module in a messagenode, in accordance with methods and systems consistent with theinvention;

FIG. 8 is a flow chart of the steps performed by a call processingmodule in a switching node, in accordance with methods and systemsconsistent with the invention;

FIG. 9 is a flow chart of the steps performed by a call routing modulein a signaling node, in accordance with methods and systems consistentwith the invention;

FIG. 10 is a block diagram of a conventional wireless telecommunicationsnetwork implementing the LocationRequest, and RoutingRequest messages;

FIG. 11 is a block diagram of a conventional wireless telecommunicationsnetwork implementing the OriginationRequest message;

FIG. 12 is a block diagram of a conventional wireless telecommunicationsnetwork implementing the TerminationRequest message;

FIG. 13 is a block diagram of a wireless telecommunications network, inaccordance with an alternate embodiment consistent with the invention;

FIGS. 14 and 14A are block diagrams of a wireless telecommunicationsnetwork, in accordance with alternate embodiments, consistent with theinvention;

FIG. 15 is a block diagram of a wireless switching node in a wirelesstelecommunication network, in accordance with methods and systemsconsistent with the invention;

FIG. 16 is a block diagram of a home location register in a wirelesstelecommunication network, in accordance with methods and systemsconsistent with the invention;

FIG. 17 is a block diagram of a directory number mapping table in a homelocation register, in accordance with methods and systems consistentwith the invention;

FIG. 18 is a block diagram of a message node in a wirelesstelecommunications network, in accordance with methods and systemsconsistent with the invention;

FIG. 19 is a block diagram of a network interface module in a messagenode in a wireless telecommunications network, in accordance withmethods and systems consistent with the invention;

FIG. 20 is a flow chart of the steps performed by a wirelesstelecommunications network when processing a TerminationRequest message,in accordance with methods and systems consistent with the invention;

FIG. 21 is a flow chart of the steps performed by a wirelesstelecommunications network when processing an OriginationRequestmessage, in accordance with methods and systems consistent with theinvention;

FIG. 22 is a flow chart of the steps performed by a home locationregister when processing a TerminationRequest or OriginationRequestmessage, in accordance with methods and systems consistent with theinvention; and

FIG. 23 is a flow chart of the steps performed when a wireless deviceattempts to contact another wireless device, in accordance with methodsand systems consistent with the invention.

DETAILED DESCRIPTION

The following description of embodiments of this invention refers to theaccompanying drawings. Where appropriate, the same reference numbers indifferent drawings refer to the same or similar elements.

In accordance with an embodiment of the invention, a network isconfigured such that network events are reported to subscribers in aplurality of formats and languages depending upon the particularsubscriber group to which a subscriber belongs. When a switching node inthe network receives a call request from a subscriber, a trigger in theswitching node is invoked to identify a designated signaling node forrouting the call. The switching node then sends a route request to thesignaling node. If during processing of the route request the signalingnode detects an event that should be reported to the subscriber, thesignaling node identifies the subscriber group associated with thesubscriber. The signaling node then selects from a directory mappingtable a directory number associated with the identified subscriber groupand the detected event and returns the selected directory number to theswitching node. Switching node then establishes the call to the messagenode, where a message associated with the determined directory number isexecuted.

FIG. 1 shows a block diagram of a telecommunications network 100, inaccordance with methods and systems consistent with the invention. Asshown, network 100 comprises switching nodes 110 and 120, a signalingnode 130, a subscriber services database 140, a message node 150, aswitching network 160, and a signaling network 170.

Switching node 110 connects via links 181, 182, and 183 to message node150, switching network 160, and signaling node 130, respectively. Links181 and 182 include, for example, N lines 181 ₁–181 _(N) and 182 ₁–182_(N) (not shown), respectively. Switching node 110 also connects vialocal loops to a telephone 111, telecommunications for the deaf (TDD)device 112, facsimile machine 113, and a desktop computer 114.

Switching node 110 may include, for example, a 5ESS™, DMS-100™ (orDMS-200™), GTD-5™ or an EWSD™ switching system manufactured by LucentTechnologies, Inc., Nortel Networks Corporation, AGCS, and Siemens,respectively. As explained below in detail, switching node 110 isconfigured to request routing information from signaling node 130 whenswitching node 110 receives call requests from telephone 111, TDD device112, facsimile machine 113, and desktop computer 114.

Similarly, switching node 120 connects via links 184, 185, and 186 tomessage node 150, switching network 160, and signaling network 170,respectively. Switching node 120 also connects via local loops to atelephone 121, TDD device 122, facsimile machine 123, and a desktopcomputer 124.

Signaling node 130 interfaces subscriber services database 140 viasignaling network 170. Signaling node 130 may include a Service ControlPoint (SCP) such as, AI-NET™, Integrated Service Control Point (ISCP™),or Service Builder™ equipment/software manufactured or provided byLucent Technologies, Inc., Telcordia Technologies, Inc., and NortelNetworks Corporation, respectively.

Subscriber services database 140 stores information about subscriberservices and may include, for example, a line information database(LIDB), call management services database (CMSDB), and/or businessservices database (BSDB). The LIDB, CMSDB, and BSDB are defined inBellcore (now Telcordia Technologies, Inc.) publication TR-NWT-001244,“Supplemental Service Control Point (SCP).”

Message node 150 may include, for example, a messaging system, whichincludes messages in a plurality of formats such as, voice, data, andTDD, and in a plurality of languages such as, English, Spanish, French,etc. Alternatively, message node 150 may be a workstation, whichincludes a plurality of stored messages and a bank of modems forreceiving calls from switching nodes 110 and 120 and switching network160.

Switching network 160 and signaling network 170 may include, forexample, a Public Switched Telephone Network (PSTN) and a SignalingSystem 7 (SS7) network, respectively.

FIG. 2 is a block diagram of switching node 110, in accordance withmethods and systems consistent with the invention. Switching node 110comprises a processor 200, which connects via bus 210 to a memory 220, asecondary storage 230, a peripheral module 240, a signaling module 250,and input terminal 260, and an output terminal 270.

Memory 220 includes a call processing module 222, an operating system224, and a trigger table 226. Call processing module 222 includes dataand software executed by processor 200 for establishing, maintaining,and terminating calls between subscribers in network 100. Operatingsystem 224 includes data and software executed by processor 200 fornon-switching functions, which include, for example, task scheduling andprocessor interrupt handling. As explained below in detail, triggertable 226 includes entries that are used to intercept call requests inswitching node 110 and to identify the associated signaling nodes suchas, signaling node 130, for routing the requested calls in network 100.

Secondary storage 230 includes a computer readable medium such as a diskdrive and a tape drive. From the tape drive, software and data may beloaded onto the disk drive, which can then be copied into memory 220.Similarly, software and data in memory 220 may be copied onto the diskdrive, which can then be loaded onto the tape drive.

Peripheral interface module 240 interfaces with links 181 and 182, whichconnect switching node 110 to message node 150 and switching network160, respectively.

Signaling interface module 250 transmits to and receives from signalingnode 130 signaling information such as, Advanced Intelligent Network(AIN) messages. For example, signaling interface module 250 convertssignaling information generated by call processing module 222 into AINmessages and transmits the messages to signaling node 130. Likewise,signaling interface module 250 receives AIN messages from signaling node130 and converts the messages into an internal format for processing bycall processing module 222.

Input terminal 260 may include an input device such as, a keyboard, andoutput terminal 270 may include a display device.

FIG. 3 is a block diagram of trigger table 226, in accordance withmethods and systems consistent with the invention. Trigger table 226includes K predetermined triggers shown as entries 300 ₁–300 _(K), whereeach entry includes an index field 301 and an identifier field 302. Inan embodiment where triggers 300 ₁–300 _(K) are Public Office DialingPlan (PODP) triggers, an index field 301 may include a 3, 6, or 10 digitstring such as, an area code, an area code and an office code, or adirectory number. PODP triggers are described in AIN 0.1 standardsTR-NWT-001284: Advanced Intelligent Network (AIN) 0.1 Switching SystemGeneric Requirements, Issue 1 (August 1992) and TR-NWT-001285: AdvancedIntelligent Network (AIN) 0.1 Service Control Point (SCP) ApplicationProtocol Interface Requirements, Issue 1 (August 1992), both of whichare incorporated herein by reference.

Alternatively, in an embodiment where triggers 300 ₁–300 _(K) areSpecific Digit String (SDS) triggers, an index field 301 may include anysequence of digits. SDS triggers are described in AIN 0.2 standardsGR-1298-CORE: AIN SSP, AINGR: Switching Systems (A Module Of AINGR,FR-15), Issue 4 (September 1997) and GR-1299-CORE: AINGR: Switch-ServiceControl Point (SCP)/Adjunct Interface (A Module Of AINGR, FR-15), Issue4 (September 1997), both of which are incorporated herein by reference.

An identifier field 302 includes a numeric string that identifies asignaling node associated with a calling subscriber's directory numberwhose area code, area code and office code, or directory number matchesthe associated an index field 301 in trigger table 226. For example,trigger table 226 may be configured to include a trigger entry 300 _(K),where index field 301 _(K) includes the area code associated withtelephone 111 and identifier field 302 _(K) includes a translationtype/global title address (TT/GTA) associated with signaling node 130.The TT/GTA may then be communicated to a signaling transfer point (STP)in network 100 for determining a point code associated with signalingnode 130. Alternatively, identifier field 302 _(K) may include a pointcode associated with signaling node 130, which may be used by switchingnode 110 to directly identify signaling node 130.

FIG. 4 is a block diagram of signaling node 130, in accordance withmethods and systems consistent with the invention. Signaling node 130comprises a processor 400, which connects via a bus 410 to a memory 420,a secondary storage 430, a signaling interface module 440, an inputterminal 450, and an output terminal 460.

Memory 420 includes a call routing module 422, an operating system 424,and a directory number (DN) mapping table 426. Call routing module 422includes data and software executed by processor 400 for communicatingwith subscriber services database 140 via signaling network 170.

Secondary storage 430 includes a computer readable medium such as a diskdrive and a tape drive. From the tape drive, software and data may beloaded onto the disk drive, which can then be copied into memory 420.Similarly, software and data in memory 420 may be copied onto the diskdrive, which can then be loaded onto the tape drive.

Signaling interface module 440 transmits to and receives from switchingnode 110 and signaling network 170 signaling information such as, AINmessages. For example, signaling interface module 440 converts signalinginformation generated by call routing module 422 into AIN messages andtransmits the messages to switching node 110 and signaling network 170.Likewise, signaling interface module 440 receives AIN messages fromswitching node 110 and signaling network 170 and converts the messagesinto an internal format for processing by call routing module 422.

Input terminal 450 may include an input device such as, a keyboard, andoutput terminal 460 may include a display device.

FIG. 5 is a block diagram of DN mapping table 426, in accordance withmethods and systems consistent with the invention. DN mapping table 426includes L entries 500 ₁–500 _(L), where each entry includes an indexfield 501 and a directory number field 502. An index field 501 mayinclude, for example, an event code and a subscriber group identifier,which identify an event and a subscriber group, respectively. Adirectory number field 502 includes a directory number that terminatesat message node 150.

In one embodiment, an administrator may configure DN mapping table 426such that each event code and subscriber group identifier combination isassociated with a unique directory number. The administrator may selecteach event code and subscriber group identifier combination so thatsubscriber devices namely, telephone 111, TDD device 112, and desktopcomputer 114, each receives from message node 150 messages that can beprocessed by the subscriber devices.

Accordingly, when a subscriber dials a directory number and network 100detects an event such as, an error in network 100 that must be reportedto the subscriber, that event is reported in a TDD format to asubscriber using TDD device 112, whereas the same event is reported in avoice format to a subscriber using telephone 111. Similarly, events arereported in English to a subscriber whose subscriber group profileindicates that events should be reported in English, whereas the sameevents are reported in Spanish to a subscriber whose subscriber groupprofile indicates that events should be reported in Spanish.

As shown below in detail, the administrator may configure message node150 with messages that are in a plurality of formats and languages andcorrespond to the directory numbers that appears in entries 500 ₁–500_(L) in DN mapping table 426. Thus, network 100 is configured toselectively report messages in different formats and languages,depending upon the particular subscriber group associated with a callingsubscriber and the particular event detected by network 100.

FIG. 6 is a block diagram of message node 150, in accordance withmethods and systems consistent with the invention. Message node 150comprises a processor 600, which connects via bus 610 to a memory 620, anetwork interface module 630, a secondary storage 640, an input device650, and an output device 660. Message node 150 may include a messagingsystem such as, Octel 250 manufactured by Lucent Technologies.Alternatively, message node 150 may include a computer that includes aVFX/PCI board manufactured by Dialogic, an Intel Company. Each port inthe VFX/PCI board may be connected to a line in links 181, 184, and 188.

Memory 620 includes a message server 622 and an operating system 624.Message server 622 includes data and software executed by processor 600for executing M messages 645 ₁–645 _(M) stored in secondary storage 640.Operating system 624 includes data and software executed by processor600 for managing tasks and processor interrupts.

In response to an interrupt initiated by network interface module 630,message server 622 loads into memory 620 one of messages 645 ₁–645 _(M)that corresponds to the port on which a call is detected in networkinterface module 630. Alternatively, in an embodiment where links 181,184, and 188 are provisioned as Direct Inward Dialing (DID) links,message server 622 loads into memory 620 one of messages 645 ₁–645 _(M)that corresponds to a sequence of digits (e.g. a portion or all digits)of a directory number included in the detected call.

Message server 622 then executes or plays the message loaded into memory620. After executing or playing the message, message server 622 signalsnetwork interface module 630 to terminate the call.

Secondary storage 640 stores messages 645 ₁–645 _(M) in a plurality offormats such as, voice, data, TDD, and in a plurality of languages suchas, English, Spanish, French, etc. An administrator stores messages 645₁–645 _(M) in secondary storage 640 such that each message is associatedwith a unique port in network interface module 630.

Input device 650 may include an input device such as, a keyboard, andoutput device 660 may include a display device.

Network interface module 630, which connects to links 181, 184, and 188,includes hardware and software for processing calls that arrive on links181, 184, and 188. FIG. 7 is a block diagram of network interface module630, in accordance with methods and systems consistent with theinvention. Network interface module 630 includes a processor 700, whichconnects via bus 710 to a memory 720, 3×N ports 730 ₁–730 _(N), 740₁–740 _(N), and 750 ₁–750 _(N). Ports 730 ₁–730 _(N) connect to lines181 ₁–181 _(N), respectively; ports 740 ₁–740 _(N) connect to lines 184₁–184 _(N), respectively; and ports 750 ₁–750 _(N) connect to lines 188₁–188 _(N), respectively.

Alternatively, links 181, 184, and 188 may be provisioned as DID linkssuch that calls detected at ports 730 ₁–730 _(N), 740 ₁–740 _(N), and750 ₁–750 _(N) include a portion (e.g., the last few digits) or all ofthe digits of the directory numbers associated with the calls.

Memory 720 includes a call processing module 722, which includes dataand software executed by processor 700 for processing calls that arriveon lines 181 ₁–181 _(N), 184 ₁–184 _(N), and 188 ₁–188 _(N). Callprocessing module 722 monitors ports 730 ₁–730 _(N), 740 ₁–740 _(N), and750 ₁–750 _(N), detects calls that arrive on lines 181 ₁–181 _(N), 184₁–184 _(N), and 188 ₁–188 _(N), and transmits an off-hook signal tonetwork 100 when a call is detected on any of the lines 181 ₁–181 _(N),184 ₁–184 _(N), and 188 ₁–188 _(N). When a call is detected, callprocessing module 722 initiates an interrupt in processor 600 to notifymessage server 622 as to the port on which a call is detected.

FIG. 8 is a flow chart of the steps performed by call processing module222 in switching node 110, in accordance with methods and systemsconsistent with the invention. In one embodiment, a calling subscriberdials a directory number from, for example, telephone 111 (shown inFIG. 1) to a called subscriber that uses telephone 122. As a result,call processing module 222 receives a call request from telephone 111(step 800). Call processing module 222 then invokes a trigger configuredin trigger table 226 based on the directory number of the callingsubscriber (step 810). For example, call processing module 222 invokes atrigger whose index matches a sequence of digits in the callingsubscriber's directory number such as, the area code, a combination ofthe area code and office code, the calling subscriber's full directorynumber, or any other sequence of digits.

Once invoked, the trigger identifies a signaling node, for examplesignaling node 130, for routing the calling subscriber's call.Accordingly, call processing module 222 requests a route from signalingnode 130 by sending, for example, an AIN info_analyze message whoseparameters include the called subscriber's directory number and thecalling subscriber's directory number (step 820). Call processing module222 then suspends further processing of the call until it receives aresponse from signaling node 130 (step 830).

The response from signaling node 130 may include, for example, an AINinfo_analyze_response message that includes as one of its parameters adirectory number to which call processing module 222 must route thecall. If signaling node 130 detects an event that must be reported tothe calling subscriber such as, when the called subscriber's directorynumber is out of service, network 100 lines are busy, or a segment ofnetwork 100 is down, signaling node 130 returns in theinfo_analyze_response message a directory number that terminates atmessage node 150. Otherwise, signaling node 130 returns the directorynumber of the next node in network 100 that must process the callrequest in order to establish the call between calling subscribertelephone 111 and called subscriber telephone 121.

Call processing module 222 then establishes a call using the directorynumber received from signaling node 130 (step 840). If the directorynumber terminates at message node 150, message node 150 answers the calland executes or plays a message associated with that directory number.Finally, call processing module 222 terminates the call when the callingsubscriber telephone 111 or message node 150 requests a disconnect (step850).

FIG. 9 is a flow chart of the steps performed by a call routing module422 in signaling node 130, in accordance with methods and systemsconsistent with the invention. When the calling subscriber dials adirectory number from telephone 111 to the called subscriber attelephone 122, call routing module 422 receives from switching node 110a request for a route from the calling subscriber to the calledsubscriber (step 900). For example, call routing module 422 may receivean AIN info_analyze message whose parameters include the calledsubscriber's directory number and the calling subscriber's directorynumber.

While processing the request, call routing module 422 determines whethernetwork 100 can establish the call (step 910). If call routing module422 determines that network 100 can establish the call, call routingmodule 422 determines the directory number of the next node in network100 that must process the call (step 920). Call routing module 422 thensends to switching node 110 the determined directory number in an AINinfo_analyze_response message (step 950).

If call routing module 422 determines that network 100 cannot establishthe call or detects an event that must be reported to the callingsubscriber such as, when the called subscriber's directory number is outof service or network 100 links are busy, call routing module 422determines the event code associated with that event. Call routingmodule 422 then queries subscriber service database 140, which mayinclude, for example, a LIDB database, to determine the subscriber groupidentifier associated with the calling subscriber (step 930).

After determining the subscriber group identifier of the callingsubscriber, call routing module 422 selects from DN mapping table 426 anentry whose index field 501 matches, for example, the event code and thesubscriber group identifier (step 940). Call routing module 422 thenreads the directory number in the directory number field 502 of theselected entry and sends the directory number to switching node 110 inan AIN info_analyze_response message (step 950). Accordingly, byselecting from DN mapping table 426 a predetermined directory numberthat terminates at message node 150 and that is based on the subscribergroup identifier of the calling subscriber and the event code associatedwith the detected event, signaling node 130 has identified anappropriate message in message node 150 for reporting the detected eventto the calling subscriber.

While it has been illustrated and described what are at presentconsidered to be preferred embodiments and methods of the presentinvention, it will be understood by those skilled in the art thatvarious changes and modifications may be made, and equivalents may besubstituted for elements thereof without departing from the true scopeof the invention.

In addition, many modifications may be made to adapt a particularelement, technique or implementation to the teachings of the presentinvention without departing from the central scope of the invention.Therefore, it is intended that this invention not be limited to theparticular embodiments and methods disclosed herein, but that theinvention include all embodiments falling within the scope of theappended claims.

Alternate Embodiment

The event reporting techniques described above relates to wirelinetelecommunication networks. Methods and system consistent with oneembodiment of the invention may include event reporting used in wirelesstelecommunication networks.

The following description of these alternate embodiment of thisinvention refers to the accompanying drawings. Where appropriate, thesame reference numbers in different drawings refer to the same orsimilar elements.

In accordance with an alternate embodiment of the invention, a networkis configured such that network events are reported to wirelesssubscribers, in a plurality of formats and languages depending upon theparticular subscriber group to which the wireless subscriber belongs.When a wireless switching node in the network receives a call requestfrom a wireless subscriber, via a wireline switching node, a trigger inthe wireless switching node is invoked to identify a designated locationregister for routing the call. The wireless switching node then sends anorigination request to the location register. If during processing ofthe origination request, the location register detects an event thatshould be reported to the wireless subscriber, the location registeridentifies the subscriber group associated with the wireless subscriber.The location register then selects from a directory mapping table adirectory number associated with the identified subscriber group and thedetected event and returns the selected directory number to the wirelessswitching node. Wireless switching node then establishes the call to themessage node, where a message associated with the determined directorynumber is executed.

In accordance with another embodiment of the invention, a network isconfigured such that network events are reported to entities attemptingto communicate with wireless subscribers, in a plurality of formats andlanguages depending upon the particular subscriber group to which thewireless subscriber belongs. When a wireline switching node in thenetwork receives a call request from an entity attempting to communicatewith a wireless subscriber, a trigger in the wireline switching node isinvoked to identify a designated location register for routing the call.The wireline switching node then sends a termination request to thelocation register. If during processing of the request the locationregister detects an event that should be reported to the entityattempting to communicate with the wireless subscriber, the locationregister identifies the subscriber group associated with the wirelesssubscriber. The location register then selects from a directory mappingtable a directory number associated with the identified subscriber groupand the detected event and returns the selected directory number to thewireline switching node. Wireline switching node then establishes thecall to the message node, where a message associated with the determineddirectory number is executed. The utility of this process recognizesthat if the wireless subscriber utilizes a special data type, such asTDD for communication, then those who would wish to communicate with thewireless subscriber will also be expecting this same format.

FIG. 13 shows a block diagram of a telecommunications network 1300, inaccordance with methods and systems consistent with one embodiment ofthe invention. As shown, network 1300 comprises wireline switching node1320, switching network 1330, wireless switching node 1340, homelocation register (HLR) 1350, signal transfer point (STP) 1357, messagenode 1360, message database 1380 and subscriber services database 1370.Wireline switching node 1320 connects to switching network 1330 via link1300 a. Wireline switching node 1320 also connects via local loops to awireline telephone 1310, telecommunications for the deaf (TDD) device1312, facsimile machine 1313 and a desktop computer 1314.

Wireline switching node 1320 may include, for example, a 5ESS™, DMS-100™(or DMS-200™), GTD-5™, or an EWSD™ switching system manufactured byLucent Technologies, Inc., Nortel Networks Corporation, AGCS, andSiemens, respectively.

Wireless switching node 1340 connects to switching network 1330, HLR1350 and message node 1360 via links 1300 b, 1300 c and 1300 frespectively. HLR 1350 further connects to subscriber services database1370 via link 1300 g.

Wireless switching node 1340 may include, for example, a 5ESS™ orDMS-MTX™ switching system manufactured by Lucent Technologies, Inc. orNortel Networks Corporation, respectively.

Signal Transfer Point 1357 routes signaling messages, such as AdvancedIntelligent Network (AIN) IS-41, in telecommunications network 1300. Itshould be noted that STP 1357 may represent one or more STPs that arerequired to perform the transfer of messages. Furthermore, thecommunications between home wireless switch 1340 and HLR 1350, may takeplace directly without STP 1357.

Home location register 1350 stores information about wirelesssubscribers in telecommunications network 1300 such as, the currentlocation of a wireless device associated with a subscriber, billinginformation, and services that the wireless subscriber is authorized touse.

Message node 1360 may include, for example, a messaging system, whichincludes messages in a plurality of formats such as, voice, data, andTDD, and in a plurality of languages such as, English, Spanish, French,etc. Alternatively, message node 1360 may be a workstation, whichincludes a plurality of stored messages housed in message database 1380and a bank of modems for receiving calls from wireless switching node1340.

Subscriber services database 1370 stores information about subscriberservices and may include, for example, a line information database(LIDB), call management services database (CMSDB), and/or businessservices database (BSDB). The LIDB, CMSDB, and BSDB are defined inBellcore (now Telcordia Technologies, Inc.) publication TR-NWT-001244,“Supplemental Service Control Point (SCP).”

Switching network 1330 may include, for example, a Public SwitchedTelephone Network/Interchange Carrier (PSTN/IX).

Call processing in telecommunications network 1300 will be explained indetail below with reference to FIG. 20.

FIG. 14 shows a block diagram of a telecommunications network 1400, inaccordance with methods and systems consistent with one embodiment ofthe invention. As shown, network 1400 comprises wireless device 1410,antenna 1420, visited wireless switching node 1430, visited locationregister (VLR) 1440, signal transfer points (STPs) 1447 and 1450, homelocation register (HLR) 1460, message node 1470 and subscriber servicesdatabase 1480.

Wireless device 1410 may be interfaced with special format communicationdevices such as a telecommunications for the deaf (TDD) device or alaptop computer.

Wireless switching node 1430 connects to VLR 1440 and message node 1470via links 1400 b and 1400 e respectively. Visited location register 1440connects with STP 1450 via link 1400 g. STP 1450 further connects withhome location register 1460 via link 1400 f. Message node 1470 connectsto subscriber services database 1480.

Wireless switching node 1430 may include, for example, a 5ESS™ orDMS-MTX™ switching system manufactured by Lucent Technologies, Inc. orNortel Networks Corporation, respectively.

Home location register 1460 stores information about wirelesssubscribers in telecommunications network 1400 such as, the currentlocation of a wireless device associated with a subscriber, billinginformation, and services that the wireless subscriber is authorized touse. Visitor location register 1440 stores information about the currentlocation of wireless device 1410 when the wireless device is activatedoutside of its home area.

Signal Transfer Points 1447 and 1450, route signaling messages, such asAdvanced Intelligent Network (AIN) IS-41, in telecommunications network1400. It should be noted that STPs 1447 and 1450 may represent one ormore STPs that are required to perform the transfer of messages.Furthermore, the communications between visited wireless switch 1430 andVLR 1440, and between VLR 1440 and HLR 1460, may take place directlywithout STPs 1447 andl250, respectively.

Message node 1470 may include, for example, a messaging system, whichincludes messages in a plurality of formats such as, voice, data, andTDD, and in a plurality of languages such as, English, Spanish, French,etc. Alternatively, message node 1470 may be a workstation, whichincludes a plurality of stored messages and a bank of modems forreceiving calls from wireless switching node 1430.

Subscriber services database 1480 stores information about subscriberservices and may include, for example, a line information database(LIDB), call management services database (CMSDB), and/or businessservices database (BSDB). The LIDB, CMSDB, and BSDB are defined inBellcore (now Telcordia Technologies, Inc.) publication TR-NWT-001244,“Supplemental Service Control Point (SCP).”

Call processing in telecommunications network 1400 will be explained indetail below with reference to FIG. 21.

FIG. 14A shows a block diagram of a telecommunications network 1400A, inaccordance with methods and systems consistent with one embodiment ofthe invention. As shown, network 1400A comprises wireless devices 1410Aand 1470A, antennae 1415A and 1465A, wireless switching nodes 1420A and1460A, location registers 1430A and 1450A, signal transfer points (STPs)1425A and 1455A, PSTN 1435A, message nodes 1440A and 1475A andsubscriber services databases 1445A and 1480A.

Wireless devices 1410A and 1470A may be interfaced with special formatcommunication devices such as a telecommunications for the deaf (TDD)device or a laptop computer.

Wireless switching nodes 1420A and 1460A connect to a respectivelocation register 1430A and 1450A, via STPs 1425A and 1455A,respectively. Wireless switching nodes 1420A and 1460A also connect withPSTN 1435A. Wireless switching nodes 1420A and 1460A further connect tomessage nodes 1440A and 1475A, respectively.

Wireless switching nodes 1420A and 1460A may include, for example, a5ESS™ or DMS-MTX™ switching system manufactured by Lucent Technologies,Inc. or Nortel Networks Corporation, respectively.

Location registers 1430A and 1450A stores information about wirelesssubscribers in telecommunications network 1400A such as, the currentlocation of a wireless device associated with a subscriber, billinginformation, and services that the wireless subscriber is authorized touse.

Signal Transfer Points 1425A and 1455A route signaling messages, such asAdvanced Intelligent Network (AIN) IS-41, in telecommunications network1400A. It should be noted that STPs 1425A and 1455A may represent one ormore STPs that are required to perform the transfer of messages.Furthermore, the communications between wireless switches 1420A, 1460Aand location registers 1430A, 1450A, may take place directly withoutSTPs 1425A and1455A, respectively.

Message nodes 1440A and 1475A may include, for example, a messagingsystem, which includes messages in a plurality of formats such as,voice, data, and TDD, and in a plurality of languages such as, English,Spanish, French, etc. Alternatively, message nodes 1440A and 1475A maybe a workstation, which includes a plurality of stored messages and abank of modems for receiving calls from wireless switching nodes 1420Aand 1460A, respectively.

Subscriber services databases 1445A and 1480A store information aboutsubscriber services and may include, for example, a line informationdatabase (LIDB), call management services database (CMSDB), and/orbusiness services database (BSDB). The LIDB, CMSDB, and BSDB are definedin Bellcore (now Telcordia Technologies, Inc.) publicationTR-NWT-001244, “Supplemental Service Control Point (SCP).”

Call processing in telecommunications network 1400A will be explained indetail below with reference to FIG. 23.

FIG. 15 is a block diagram of wireless switching nodes 1340 and 1430, inaccordance with methods and systems consistent with the invention.Wireless switching node 1340 will be described, but it should beunderstood that wireless switching node 1430 comprises similar elementsand functions, other than being a visited wireless switching nodeconnected to different entities in network 1400. Wireless switching node1340 comprises a processor 1500, which connects via bus 1510 to a memory1520, a secondary storage 1530, a peripheral module 1540, a signalingmodule 1550, and input terminal 1560, and an output terminal 1570.

Memory 1520 includes a call processing module 1522, an operating system1524, and a trigger table 1526. Call processing module 1522 includesdata and software executed by processor 1500 for establishing,maintaining, and terminating calls between wireless subscribers in thetelecommunications network. Operating system 1524 includes data andsoftware executed by processor 1500 for non-switching functions, whichinclude, for example, task scheduling and processor interrupt handling.Trigger table 1526 includes entries that are used to intercept callrequests in wireless switching node and to identify the associatedlocation register.

Secondary storage 1530 includes a computer readable medium such as adisk drive and a tape drive. From the tape drive, software and data maybe loaded onto the disk drive, which can then be copied into memory1520. Similarly, software and data in memory 1520 may be copied onto thedisk drive, which can then be loaded onto the tape drive.

Peripheral interface module 1540 interfaces with the message node andPSTN/IX 1330.

Signaling interface module 1550 transmits to and receives from locationregister 1350 signaling information such as, Advanced IntelligentNetwork (AIN) messages. For example, signaling interface module 1550converts signaling information generated by call processing module 1522into AIN messages and transmits the messages to location register 1350.For network 1300, these messages include TerminationRequest messages.Likewise, signaling interface module 1550 receives AIN messages fromlocation register 1350 and converts the messages into an internal formatfor processing by call processing module 1522.

Input terminal 1560 may include an input device such as, a keyboard, andoutput terminal 1570 may include a display device.

FIG. 16 is a block diagram of home location register (HLR) 1350 or 1460,in accordance with methods and systems consistent with the invention.HLR 1350 will be described, however it should be understood that HLR1460 comprises of similar elements and functions. Home location register1350 comprises a processor 1600, which connects via a bus 1610 to amemory 1620, a secondary storage 1630, a signaling interface module1640, an input terminal 1650, and an output terminal 1660.

Memory 1620 includes a call routing module 1622, an operating system1624, and a directory number (DN) mapping table 1626. Call routingmodule 1622 includes data and software executed by processor 1600 forcommunicating with subscriber services database 1370.

Secondary storage 1630 includes a computer readable medium such as adisk drive and a tape drive. From the tape drive, software and data maybe loaded onto the disk drive, which can then be copied into memory1620. Similarly, software and data in memory 1370 may be copied onto thedisk drive, which can then be loaded onto the tape drive.

Signaling interface module 1640 transmits to and receives from wirelessswitching node 1340 signaling information such as, AIN messages. Forexample, signaling interface module 1640 converts signaling informationgenerated by call routing module 1622 into AIN messages and transmitsthe messages to wireless switching node 1340. Likewise, signalinginterface module 1640 receives AIN messages from wireless switching node1340 and converts the messages into an internal format for processing bycall routing module 1622.

With respect to network 1400, HLR 1460's signaling interface module 1640transmits and receives from VLR 1440, via STP 1450, signalinginformation such as, AIN messages. For example, signaling interfacemodule 1640 converts signaling information generated by call routingmodule 1622 into AIN messages and transmits the messages to STP 1450 forpassage to VLR 1440. Likewise, signaling interface module 1640 receivesAIN messages from STP 1450 and converts the messages into an internalformat for processing by call routing module 1622.

Input terminal 1650 may include an input device such as, a keyboard, andoutput terminal 1660 may include a display device.

FIG. 17 is a block diagram of DN mapping table 1626, in accordance withmethods and systems consistent with the invention. DN mapping table 1626includes L entries 1700 ₁–1700 _(L), where each entry includes an indexfield 1701 and a directory number field 1702. An index field 1701 mayinclude, for example, an event code and a subscriber group identifier,which identify an event and a subscriber group, respectively. Adirectory number field 1702 includes a directory number that terminatesat message node 1360.

In one embodiment, an administrator may configure DN mapping table 1626such that each event code and subscriber group identifier combination isassociated with a unique directory number. The administrator may selecteach event code and subscriber group identifier combination so that userdevices namely, telephone 1310, TDD device 1312, and desktop computer1314, each receives from message node 1360 messages that can beprocessed by the user devices.

Accordingly, when a user attempting to contact a wireless subscriberdials a directory number and network 1300 detects an event such as, anerror in network 1300 that must be reported to the user, that event isreported in a TDD format to a user attempting to communicate with awireless subscriber using a wireless device interfaced with a TDDdevice, whereas the same event is reported in a voice format to a userattempting to communicate with a wireless subscriber using voiceformats. Similarly, events are reported in English to a user attemptingto communicate with a wireless subscriber whose subscriber group profileindicates that events should be reported in English, whereas the sameevents are reported in Spanish to a user attempting to communicate witha wireless subscriber whose subscriber group profile indicates thatevents should be reported in Spanish.

In another embodiment, an administrator may configure DN mapping table1626 such that each event code and subscriber group identifiercombination is associated with a unique directory number. With referenceto FIG. 14, the administrator may select each event code and subscribergroup identifier combination so that subscriber device namely, wirelessdevice 1410, receives from message node 1470 messages that can beprocessed by the user devices.

Accordingly, for wireless subscriber applications as described in FIG.14, when a wireless subscriber dials a directory number and network 1400detects an event such as, an error in network 1400 that must be reportedto the wireless subscriber, that event is reported in a TDD format to asubscriber using TDD a device, whereas the same event is reported in avoice format to a wireless subscriber using voice formats. Similarly,events are reported in English to a wireless subscriber whose subscribergroup profile indicates that events should be reported in English,whereas the same events are reported in Spanish to a wireless subscriberwhose subscriber group profile indicates that events should be reportedin Spanish.

As shown below in detail, the administrator may configure message nodes1360 and 1470 with messages that are in a plurality of formats andlanguages and correspond to the directory numbers that appears inentries 1700 ₁–1700 _(L) in DN mapping table 1626. Thus, networks 1300and/or 1400 are configured to selectively report messages in differentformats and languages, depending upon the particular subscriber groupassociated with a wireless subscriber and the particular event detectedby network 1300 and/or 1400.

FIG. 18 is a block diagram of message node 1360, in accordance withmethods and systems consistent with the invention. Although message node1360 is described in detail, it should be understood that message node1470 comprises similar elements and performs the same functions asmessage node 1360. Message node 1360 comprises a processor 1800, whichconnects via bus 1810 to a memory 1820, a network interface module 1830,a secondary storage 1840, an input device 1850, and an output device1860. Message node 1360 may include a messaging system such as, Octel250 manufactured by Lucent Technologies. Alternatively, message node1360 may include a computer that includes a VFX/PCI board manufacturedby Dialogic, an Intel Company.

Memory 1820 includes a message server 1822 and an operating system 1824.Message server 1822 includes data and software executed by processor1800 for executing M messages 1845 ₁–1845 _(M) stored in secondarystorage 1840. Operating system 1824 includes data and software executedby processor 1800 for managing tasks and processor interrupts.

In response to an interrupt initiated by network interface module 1830,message server 1822 loads into memory 1820 one of messages 1845 ₁–1845_(M) that corresponds to the port on which a call is detected in networkinterface module 1830. Alternatively, in an embodiment where link 1800 fis provisioned as Direct Inward Dialing (DID) links, message server 1822loads into memory 1820 one of messages 1845 ₁–1845 _(M) that correspondsto a sequence of digits (e.g. a portion or all digits) of a directorynumber included in the detected call.

Message server 1822 then executes or plays the message loaded intomemory 1820. After executing or playing the message, message server 1822signals network interface module 1830 to terminate the call.

Secondary storage 1840 stores messages 1845 ₁–1845 _(M) in a pluralityof formats such as, voice, data, TDD, and in a plurality of languagessuch as, English, Spanish, French, etc. An administrator stores messages1845 ₁–1845 _(M) in secondary storage 1840 such that each message isassociated with a unique port in network interface module 1830.

Input device 1850 may include an input device such as, a keyboard, andoutput device 1860 may include a display device.

Network interface module 1830, which connects to link 1300 f, includeshardware and software for processing calls that arrive on link 1300 f.FIG. 19 is a block diagram of network interface module 1830, inaccordance with methods and systems consistent with the invention.Network interface module 1830 includes a processor 1900, which connectsvia bus 1910 to a memory 1920, N ports 1930 ₁–1930 _(N). Ports 1930₁–1930 _(N) connect to lines 1300 f ₁–1300 f _(N).

Alternatively, link 1300 f may be provisioned as DID links such thatcalls detected at ports 1930 ₁–1930 _(N) include a portion (e.g., thelast few digits) or all of the digits of the directory numbersassociated with the calls.

Memory 1920 includes a call processing module 1922, which includes dataand software executed by processor 1900 for processing calls that arriveon lines 1300 f ₁–1300 f _(N). Call processing module 1922 monitorsports 1930 ₁–1930 _(N), detects calls that arrive on lines 1300 f ₁–1300f _(N), and transmits an off-hook signal to network 1300 when a call isdetected on any of the lines 1300 f ₁–1300 f _(N). When a call isdetected, call processing module 1922 initiates an interrupt inprocessor 1800 to notify message server 1822 as to the port on which acall is detected.

FIG. 20 is a flow chart of the steps performed by network 1300 whenprocessing a TerminationRequest in accordance with methods and systemsconsistent with the invention. The process begins when any one of thewireline devices 1310, 1312, 1313 or 1314 attempts to call a wirelesssubscriber device by dialing a mobile number associated with thewireless device (Step 2000). The call request is passed to wirelineswitching node 1320, which analyzes the dialed number and sends it tothe wireless switching node 1340 via PSTN/IXC and links 1300 a, 1340 b(Step 2010).

Upon receiving the request, wireless switching node 1340 recognizesparameters previously provided by HLR 1350, causing a terminationtrigger to be invoked, and subsequently generates a TerminationRequest1300 d which is sent to HLR 1350 (Step 2020), possibly through STP 1357.While processing the call request, HLR 1350 checks to determine whetherthe call cannot be completed by virtue of a network event or error (Step2030).

If no error or event occurred, HLR 1350 determines a directory number DNfor routing the call (Step 2040), and sends the DN to wireless switchingnode 1340, possibly through STP 1357. Using the DN, network 1300eventually establishes a connection between the wireline devicerequesting the call and the wireless subscriber device (Step 2050).However, if a network event is detected by HLR 1350, a mapped directorynumber is determined and sent back to wireless switching node 1340 in aTerminationRequest response 1300 e (Step A). This process will bedescribed in further detail with reference to FIG. 22.

Upon receiving the TerminationRequest response, with the appended mappeddirectory number (B), the wireless switching node 1340 sets a path tothe message node 1360 over a network trunk group 1300 f (Step 2060). Themessage node 1360 maps the received mapped DN to a predetermined messagein suitable format stored in an internal database 1380 (Step 2070). Thepredetermined message is passed and presented to the wireline device(1310, 1312, 1313 or 1314) which generated the call request (Step 2080).

The utility of this process recognizes that if the wireless subscriberutilizes a special data type, such as TDD for communication, then thewireline devices attempting to communicate with the wireless subscriberwill also be expecting the same format.

FIG. 21 is a flow chart of the steps performed by network 1400 whenprocessing an OriginationRequest in accordance with methods and systemsconsistent with the invention. The process begins when wireless device1410 originates a call request at wireless switching node 1430 by way ofantenna 1420 and link 1400 a (Step 2110).

Wireless switching node 1430 receives the call request, examinesparameters previously provided by HLR 1460, causing a originationtrigger to be invoked. This results in an OriginationRequest 1400 c tobe sent to VLR 1440, which is associated with wireless switching node1430. The OriginationRequest is sent possibly through STP 1447. VLR 1440passes the OriginationRequest 1400 c to HLR 1460. (Step 2120), possiblythrough STP 1450.

HLR 1460 receives the OriginationRequest 1400 c, and while processingthe call request, it checks to determine whether the call cannot becompleted by virtue of a network event or error (Step 2130). If no erroror event occurred, HLR 1460 determines a directory number DN for routingthe call (Step 2140) and sends the DN to wireless switching node 1430.Network 1400 uses the DN to eventually establish a connection betweenthe wireless device 1410 requesting the call and the entity the wirelesssubscriber is attempting call (Step 2150).

However, if a network event is detected by HLR 1460, a mapped directorynumber is determined and sent back to wireless switching node 1430 in anOriginationRequest response 1400 d, via VLR 1440 and possible throughSTPs 1450 and 1447 (A). This process will be described in further detailwith reference to FIG. 22.

Upon receiving the OriginationRequest response with the appended mappeddirectory number (C), the wireless switching node 1430 sets a path tothe message node 1470 over a network trunk group 1400 e (Step 2160). Themessage node 1470 maps the received mapped DN to a predetermined messagein suitable format stored in an internal database 1480 (Step 2170). Thepredetermined message is passed and presented to the wireless device1410 which generated the call request (Step 2180).

FIG. 22 is a flow chart of the steps performed by HLRs 1350 and 1460,when processing a TerminationRequest or OriginationRequest,respectively, when an error or event occurs, in accordance with methodsand systems consistent with the invention.

When HLR 1350, 1460 determines that the network cannot establish thecall or detects an event that must be reported, HLR 1350, 1460determines the event code associated with that event. HLR 1350, 1460then queries subscriber service database 1370,1480 respectively, whichmay include, for example, a LIDB database, to determine the subscribergroup identifier associated with the calling subscriber (Step 2210).

After determining the subscriber group identifier of the wirelesssubscriber, HLR1350, 1460 selects from DN mapping table 1626 an entrywhose index field 1701 matches, for example, the event code and thesubscriber group identifier (Step 2220). HLR 1350, 1460 then reads thedirectory number in the directory number field 1702 of the selectedentry. Depending upon the type of request (Step 2230), the appropriateHLR places the mapped DN into the corresponding response,TerminationRequest response generated by HLR 1350 (Step 2240), orOriginationRequest response generated by HLR 1460 (Step 2260).

With respect to the operations for HLR 1340, the TerminationRequestresponse 1300 e is sent back to the wireless switching node 1340,possibly through STP 1357 (Step 2250), where the message node iscontacted for message delivery, as described above with respect to FIG.20 (B).

With respect to the operations for HLR 1460, the OriginationRequestresponse 1400 d is sent back to wireless switching node 1430, via VLR1440 and possibly STPs 1450 and 1447 (Step 2270), where the message nodeis contacted for message delivery to the wireless subscriber, asdescribed above with respect to FIG. 21(C).

Accordingly, by selecting from DN mapping table 1626 a predetermineddirectory number that terminates at message node 1360, 1470 and that isbased on the subscriber group identifier of the wireless subscriber andthe event code associated with the detected event, HLR 1350, 1460 hasidentified an appropriate message in message node 1360, 1470 forreporting the detected event.

FIG. 23 is a flow chart of the steps performed by network 1400A whenprocessing a wireless to wireless device communication, in accordancewith methods and systems consistent with the invention. The processbegins when wireless device 1410A originates a call request to wirelessdevice 1470A. The call is request is sent to wireless switching node1420A by way of antenna 1415A (Step 2310).

Wireless switching node 1420A receives the call request, examinesparameters previously provided by location register 1430A, causing aorigination trigger to be invoked. This results in an OriginationRequestto be sent to location register 1430A, which is associated with wirelessswitching node 1420A. The OriginationRequest is sent possibly throughSTP 1425A. (Step 2315).

Location register 1430A receives the OriginationRequest, and whileprocessing the call request, it checks to determine whether the callcannot be completed by virtue of a network event or error (Step 2320).If no error or event occurred, location register 1430A determines adirectory number DN for routing the call (Step 2325). Network 1400A usesthe DN to eventually establish a connection between the wireless device1410A and wireless device 1470A, via PSTN 1435A. (Step 2330).

However, if a network event is detected by location register 1430A, amapped directory number is determined and sent back to wirelessswitching node 1420A in an OriginationRequest response, possibly throughSTP 1425A. (D).

Referring back to step 2330, upon receiving the request, wirelessswitching node 1460A recognizes parameters previously provided bylocation register 1450A, causing a termination trigger to be invoked,and subsequently generates a TerminationRequest which is sent tolocation register 1450A (Step 2335), possibly through STP 1355A. Whileprocessing the call request, location register 1450A checks to determinewhether the call cannot be completed by virtue of a network event orerror (Step 2340).

If no error or event occurred, location register 1450A determines adirectory number DN for routing the call (Step 2345), and sends the DNto wireless switching node 1460A, possibly through STP 1455A. Using theDN, network 1400A eventually establishes a connection between thewireless device 1410A and wireless device 1470A (Step 2350). However, ifa network event is detected by location register 1450A, a mappeddirectory number is determined and sent back to wireless switching node1460A in a TerminationRequest response (D).

In the event a network error event has been detected by locationregisters 1430A and 1450A, they determine the event code associated withthe network event. Location registers 1430A and 1450A then querysubscriber service database 1445A and 1480A respectively, which mayinclude, for example, a LIDB database, to determine the subscriber groupidentifier associated with the calling subscriber (Step 2355).

After determining the subscriber group identifier of the wirelesssubscriber, location registers 1430A and 1450A select from a DN mappingtable, an entry whose index field matches, for example, the event codeand the subscriber group identifier (Step 2360). Location registers1430A and 1450A then read the directory number in the directory numberfield of the selected entry. Depending upon the type of request (Step2365), the appropriate location register places the mapped DN into thecorresponding response: TerminationRequest response generated bylocation register 1350A (Step 2370); or OriginationRequest responsegenerated by location register 1430A (Step 2380).

With respect to the operations for the TerminationRequest response, theresponse is sent back to the wireless switching node 1460A, possiblythrough STP 1355A (Step 2375), where message node 1475A is contacted formessage delivery. Upon receiving the TerminationRequest response withthe appended mapped directory number, the wireless switching node 1460Asets a path to the message node 1475A over a network trunk group (Step2390). The message node 1475A maps the received mapped DN to apredetermined message in suitable format stored in an internal database1480A (Step 2392). The predetermined message is passed and presented tothe device which generated the call request, in this case wirelessdevice 1410A (Step 2395).

With respect to the operations for the OriginationRequest response, theresponse is sent back to wireless switching node 1420A, possibly throughSTPs 1425A (Step 2385), where message node 1440A is contacted formessage delivery to the wireless subscriber. Upon receiving theOriginationRequest response with the appended mapped directory number,the wireless switching node 1420A sets a path to the message node 1440Aover a network trunk group (Step 2390). The message node 1440A maps thereceived mapped DN to a predetermined message in suitable format storedin an internal database 1445A (Step 2392). The predetermined message ispassed and presented to the wireless device 1410A which generated thecall request (Step 2395).

While it has been illustrated and described what are at presentconsidered to be preferred embodiments and methods of the presentinvention, it will be understood by those skilled in the art thatvarious changes and modifications may be made, and equivalents may besubstituted for elements thereof without departing from the true scopeof the invention.

1. A method for reporting events in a wireless intelligent network, saidmethod comprises the steps of: identifying a group associated with awireless subscriber when an event that indicates an error in routing acall to the wireless subscriber is detected; determining a directingnumber associated with the identified group and the detected event;establishing a call between the wireless subscriber and a message nodein the network using the determined directory number; generating amessage by the message node based on the directory number and a profileassociated with the identified group; and reporting the message to thewireless subscriber.
 2. The method of claim 1, wherein the identifyingstep comprises the step of: identifying a subscriber group associatedwith the wireless subscriber when the event is detected.
 3. The methodof claim 1, wherein the identifying step comprises the step of:identifying the group when the detected event is associated with a callrequested by the wireless subscriber.
 4. The method of claim 1, whereinthe identifying step comprises the step of: identifying the group whenthe detected event is associated with a call that is requested by thewireless subscriber and that cannot be established in the network. 5.The method of claim 1, wherein the identifying step comprises the stepof: retrieving from a subscriber services database in the network agroup identifier associated with the calling wireless subscriber.
 6. Themethod of claim 1, wherein the determining step comprises the step of:selecting the directory number from a table that includes one or morepredetermined directory numbers indexed by event identifiers and groupidentifiers.
 7. The method of claim 1, wherein the reporting stepcomprises the step of: executing the message in a voice format.
 8. Themethod of claim 1, wherein the reporting step comprises the step of:executing the message in a telecommunications device for deaf (TDD)format.
 9. The method of claim 1, wherein the reporting step comprisesthe step of: executing the message in a data format.
 10. A method forreporting events that indicate at least one error associated with callsrequested by wireless subscribers in a wireless intelligent network,wherein the wireless subscribers are members of subscriber groups, saidmethod comprises the steps of: associating one or more directory numberswith the events and the subscriber groups; storing, in a message node inthe network, messages corresponding to the associated directory numbers,respectively; establishing calls, when the network detects the eventsthat indicate the at least one error, between the message node and asubscriber based on the directory numbers, wherein the message nodeselects one or more messages that are provided to a subscriber based onthe directory numbers and the associated subscriber group.
 11. Themethod of claim 10, wherein the storing step comprises the step of:storing the messages in a plurality of predetermined formats.
 12. Themethod of claim 10, wherein the storing step comprises the step of:storing the messages in a plurality of predetermined languages.
 13. Themethod of claim 10, wherein the establishing step comprises the step of:establishing the calls to the message node when a location register inthe network detects the events.
 14. The method of claim 10, wherein theestablishing step comprises the step of: requesting a route from alocation register in the network when one of the wireless subscribersrequests a call to another one of the wireless subscribers.
 15. A methodfor reporting events in a wireless intelligent network comprising aswitching node and a message node interconnected by a network, saidmethod comprises the steps of: receiving, at the switching node, arequest for establishing a call from a wireline subscriber to a wirelesssubscriber in the wireless intelligent network; identifying a locationregister in the wireless intelligent network for routing the call;receiving, at the switching node, a directory number from the identifiedlocation register; and establishing the call from the wirelinesubscriber to the message node based on the received directory numberand a subscriber group associated with the wireless subscriber, when anevent that indicates an error associated with the call is detected. 16.The method of claim 15, further comprising the step of: terminating thecall established from the wireline subscriber to the message node when arequest for disconnect is received from the wireline subscriber or themessage node.
 17. The method of claim 15, wherein the receiving stepcomprises the step of: receiving the directory number in a call requestresponse generated by the location register.
 18. A method for reportingevents in a wireless network comprising a switching node, a locationregister, and a message node, said method comprises the steps of:receiving, at the location register, a request from the switching nodefor routing a call from a first subscriber to a second subscriber in thewireless network; identifying a group associated with the firstsubscriber when an event that indicates an error associated with thecall is detected; selecting a directory number based on the identifiedgroup and the detected event; and sending the selected directory numberto the switching node such that the call is established from the firstsubscriber to the message node to allow the message node to provide tothe first subscriber a message that is selected based on the directorynumber and a profile associated with the identified group.
 19. Themethod of claim 18, wherein the selecting step comprises the step of:selecting the directory number from a plurality of predetermineddirectory numbers that are indexed by event identifiers and groupidentifiers.
 20. A wireless switching node, comprising: a memoryincluding: a structure for identifying a location registerrepresentative of an identified group and an event that indicates anerror associated with a call in a wireless network when the switchingnode receives a request for establishing the call from a firstsubscriber to a second subscriber in the wireless network, wherein thestructure includes a trigger indexed by a variable number of digits in adirectory number of the first subscriber; and computer-readable code forestablishing the call from the first subscriber to a message node in thewireless network when the event is detected; and a processor forexecuting he computer-readable code.
 21. The wireless switching node ofclaim 20, wherein the structure includes a trigger in indexed by an areacode in a directory number of the first subscriber.
 22. The wirelessswitching node of claim 20, wherein the structure includes a trigger inindexed by an area code and an office code in the directory number ofthe first subscriber.
 23. A location register, comprising: a memoryincluding: a structure for storing predetermined directory numbersassociated with events that indicate errors associated with calls in awireless network and groups in the wireless intelligent network, whereinthe predetermined directory numbers correspond, respectively, to messagestored in a message node in the wireless intelligent network; andcomputer-readable code for detecting at least one of the events thatindicate errors in the wireless network when one subscriber requests acall to another subscriber, identifying a group associated with the onesubscriber requesting the call, and selecting, based on the detectedevent and the identified group, one of the stored predetermineddirectory numbers that is used to establish communications between theone subscriber and the message node and is used by the message node toselect one of the messages to be sent to the one subscriber; and aprocessor for executing the computer-readable code.
 24. A message node,comprising: a storage module for storing messages associated,respectively, with predetermined directory numbers that correspond toevents that indicate errors in a wireless intelligent network andcorrespond to groups with profiles associated with wireless subscribers;a memory including computer-readable code for selecting one of themessages based on the profiles when the wireless intelligent networkdetects at least one of the events, establishing a call to one of thepredetermined directory numbers, and providing the selected message to asubscriber associated with the one predetermined directory number; and aprocessor for executing the computer-readable code.
 25. The message nodeof claim 24, wherein the messages are stored in a plurality of formats.26. The message node of claim 24, wherein at least one of the messagesis stored in a voice format.
 27. The message node of claim 24, whereinat least one of the messages is stored in a telecommunications for deaf(TDD) format.
 28. Th message node of claim 24, wherein at least one ofthe messages is stored in a data format.
 29. The message node of claim24, wherein the messages are stored in a plurality of languages.
 30. Acomputer-readable medium capable of configuring a computer to perform amethod for reporting events in a wireless intelligent network, saidmethod comprising the steps of: receiving a request for establishing acall from a first subscriber to a second subscriber in the wirelessintelligent network; requesting a route from a location register in thenetwork; receiving from the location register a directory number;establishing the call from the first subscriber to a message node in thewireless intelligent network based on the received directory number anda subscriber group associated with the first subscriber, when an eventthat indicates an error associated with the call is detected; andproviding a message to the first subscriber based on the directorynumber, the event and a profile associated with the subscriber groupcorresponding to the first subscriber.
 31. A method for reporting eventsin a wireless intelligent network, said method comprises the steps of:identifying a group associated with a wireless subscriber when an eventthat indicates an error in routing a call to the wireless subscriber isdetected; determining a directory number from a table that includes oneor more predetermined directory numbers indexed by event identifiersthat are each associated with an event and group identifiers that areeach associated with a subscriber group; and reporting to a subscriberattempting to communicate with the wireless subscriber, a messageassociated with the determined directory number.
 32. The method of claim31, wherein the identifying step comprises the step of: identifying asubscriber group associated with the wireless subscriber when the eventis detected.
 33. The method of claim 31, wherein the identifying stepcomprises the step of: identifying the group when the detected event isassociated with a call requested to the wireless subscriber.
 34. Themethod of claim 31, therein the identifying step comprises the step of:identifying the group when the detected event is Associated with a callthat is requested by the subscriber attempting to communicate with thewireless subscriber and that cannot be established in the wirelessintelligent network.
 35. The method of claim 34, wherein the identifyingstep comprises the step of: retrieving from a subscriber servicesdatabase in the wireless intelligent network, a group identifierassociated with the wireless subscriber.
 36. The method of claim 31,wherein the reporting step comprises the step of: establishing a callfrom the wireless subscriber to a message node in the network using thedetermined directory number.
 37. The method of claim 31, wherein thereporting step comprises the step of: executing the message in a voiceformat.
 38. The method of claim 31, wherein the reporting step comprisesthe step of: executing the message in a telecommunication device fordeaf (TDD) format.
 39. The method of claim 31, wherein the reportingstep comprises the step of: executing the message in a data format.